Review



simbody api  (OpenSim Ltd)

 
  • Logo
  • About
  • News
  • Press Release
  • Team
  • Advisors
  • Partners
  • Contact
  • Bioz Stars
  • Bioz vStars
    • 90
      Buy from Supplier

    Structured Review

    OpenSim Ltd simbody api
    Orientation data of inertial measurement units (IMUs) is read as quaternions by the producer thread and saved to a buffer. Time values are saved to another buffer. The consumer thread reads data from both buffers and initiates new threads that calculate IK based on the data. IK threads output joint angle values for the model. Within an IK thread, the IK output can be sent to a visualizer window. The visualization is based on the <t>Simbody</t> ( i.e ., the physics engine used by OpenSim) <t>API</t> and not a part of our software library and hence not described here in more detail. When the program finishes, the IK output frames can be sorted in a time-ascending order and saved to file.
    Simbody Api, supplied by OpenSim Ltd, used in various techniques. Bioz Stars score: 90/100, based on 1 PubMed citations. ZERO BIAS - scores, article reviews, protocol conditions and more
    https://www.bioz.com/result/simbody api/product/OpenSim Ltd
    Average 90 stars, based on 1 article reviews
    simbody api - by Bioz Stars, 2026-03
    90/100 stars

    Images

    1) Product Images from "Open-source software library for real-time inertial measurement unit data-based inverse kinematics using OpenSim"

    Article Title: Open-source software library for real-time inertial measurement unit data-based inverse kinematics using OpenSim

    Journal: PeerJ

    doi: 10.7717/peerj.15097

    Orientation data of inertial measurement units (IMUs) is read as quaternions by the producer thread and saved to a buffer. Time values are saved to another buffer. The consumer thread reads data from both buffers and initiates new threads that calculate IK based on the data. IK threads output joint angle values for the model. Within an IK thread, the IK output can be sent to a visualizer window. The visualization is based on the Simbody ( i.e ., the physics engine used by OpenSim) API and not a part of our software library and hence not described here in more detail. When the program finishes, the IK output frames can be sorted in a time-ascending order and saved to file.
    Figure Legend Snippet: Orientation data of inertial measurement units (IMUs) is read as quaternions by the producer thread and saved to a buffer. Time values are saved to another buffer. The consumer thread reads data from both buffers and initiates new threads that calculate IK based on the data. IK threads output joint angle values for the model. Within an IK thread, the IK output can be sent to a visualizer window. The visualization is based on the Simbody ( i.e ., the physics engine used by OpenSim) API and not a part of our software library and hence not described here in more detail. When the program finishes, the IK output frames can be sorted in a time-ascending order and saved to file.

    Techniques Used: Software



    Similar Products

    simbody api  (OpenSim Ltd)
    90
    OpenSim Ltd simbody api
    Orientation data of inertial measurement units (IMUs) is read as quaternions by the producer thread and saved to a buffer. Time values are saved to another buffer. The consumer thread reads data from both buffers and initiates new threads that calculate IK based on the data. IK threads output joint angle values for the model. Within an IK thread, the IK output can be sent to a visualizer window. The visualization is based on the <t>Simbody</t> ( i.e ., the physics engine used by OpenSim) <t>API</t> and not a part of our software library and hence not described here in more detail. When the program finishes, the IK output frames can be sorted in a time-ascending order and saved to file.
    Simbody Api, supplied by OpenSim Ltd, used in various techniques. Bioz Stars score: 90/100, based on 1 PubMed citations. ZERO BIAS - scores, article reviews, protocol conditions and more
    https://www.bioz.com/result/simbody api/product/OpenSim Ltd
    Average 90 stars, based on 1 article reviews
    simbody api - by Bioz Stars, 2026-03
    90/100 stars
    		  Buy from Supplier
    api simbody  (OpenSim Ltd)
    90
    OpenSim Ltd api simbody
    OpenSim Layers. The base layer is the computational layer provided by <t>Simbody</t> (in blue). Simbody components, numerical methods (e.g. integrators, optimizers) and other computational resources are available to all levels within the OpenSim <t>API,</t> and to users of the OpenSim API (right-hand side). The next layer up is the modelling layer (green), this defines the model and all its components. A model component is any part of the model that contributes to the system equations, which include degrees of freedom, constraints, forces, and user defined components (e.g. sensors) with their own dynamics and state variables. The modeling layer is followed by the analysis layer (orange), which is an abstraction for any algorithm that creates or modifies models (a modeler), solves the model system of equations for particular values (solver, e.g. an inverse dynamics solver) and/or collects and writes values from a model (with or without the help of a solver) to file or display (a reporter). The top layer is the application layer (red) which does not provide an API but is a consumer of the OpenSim API to generate applications like the OpenSim GUI or dynamic libraries (plugins) encapsulating model components and/or analyses that are loaded and executed by the GUI at run-time.
    Api Simbody, supplied by OpenSim Ltd, used in various techniques. Bioz Stars score: 90/100, based on 1 PubMed citations. ZERO BIAS - scores, article reviews, protocol conditions and more
    https://www.bioz.com/result/api simbody/product/OpenSim Ltd
    Average 90 stars, based on 1 article reviews
    api simbody - by Bioz Stars, 2026-03
    90/100 stars
    		  Buy from Supplier

    Image Search Results


    Orientation data of inertial measurement units (IMUs) is read as quaternions by the producer thread and saved to a buffer. Time values are saved to another buffer. The consumer thread reads data from both buffers and initiates new threads that calculate IK based on the data. IK threads output joint angle values for the model. Within an IK thread, the IK output can be sent to a visualizer window. The visualization is based on the Simbody ( i.e ., the physics engine used by OpenSim) API and not a part of our software library and hence not described here in more detail. When the program finishes, the IK output frames can be sorted in a time-ascending order and saved to file.

    Journal: PeerJ

    Article Title: Open-source software library for real-time inertial measurement unit data-based inverse kinematics using OpenSim

    doi: 10.7717/peerj.15097

    Figure Lengend Snippet: Orientation data of inertial measurement units (IMUs) is read as quaternions by the producer thread and saved to a buffer. Time values are saved to another buffer. The consumer thread reads data from both buffers and initiates new threads that calculate IK based on the data. IK threads output joint angle values for the model. Within an IK thread, the IK output can be sent to a visualizer window. The visualization is based on the Simbody ( i.e ., the physics engine used by OpenSim) API and not a part of our software library and hence not described here in more detail. When the program finishes, the IK output frames can be sorted in a time-ascending order and saved to file.

    Article Snippet: Our software library includes an option to visualize motion like in OpenSim GUI by invoking methods from the Simbody API (namely, from the SimTK::Visualizer class), which OpenSim API is built upon.

    Techniques: Software

    OpenSim Layers. The base layer is the computational layer provided by Simbody (in blue). Simbody components, numerical methods (e.g. integrators, optimizers) and other computational resources are available to all levels within the OpenSim API, and to users of the OpenSim API (right-hand side). The next layer up is the modelling layer (green), this defines the model and all its components. A model component is any part of the model that contributes to the system equations, which include degrees of freedom, constraints, forces, and user defined components (e.g. sensors) with their own dynamics and state variables. The modeling layer is followed by the analysis layer (orange), which is an abstraction for any algorithm that creates or modifies models (a modeler), solves the model system of equations for particular values (solver, e.g. an inverse dynamics solver) and/or collects and writes values from a model (with or without the help of a solver) to file or display (a reporter). The top layer is the application layer (red) which does not provide an API but is a consumer of the OpenSim API to generate applications like the OpenSim GUI or dynamic libraries (plugins) encapsulating model components and/or analyses that are loaded and executed by the GUI at run-time.

    Journal: Procedia IUTAM

    Article Title: OpenSim: a musculoskeletal modeling and simulation framework for in silico investigations and exchange

    doi: 10.1016/j.piutam.2011.04.021

    Figure Lengend Snippet: OpenSim Layers. The base layer is the computational layer provided by Simbody (in blue). Simbody components, numerical methods (e.g. integrators, optimizers) and other computational resources are available to all levels within the OpenSim API, and to users of the OpenSim API (right-hand side). The next layer up is the modelling layer (green), this defines the model and all its components. A model component is any part of the model that contributes to the system equations, which include degrees of freedom, constraints, forces, and user defined components (e.g. sensors) with their own dynamics and state variables. The modeling layer is followed by the analysis layer (orange), which is an abstraction for any algorithm that creates or modifies models (a modeler), solves the model system of equations for particular values (solver, e.g. an inverse dynamics solver) and/or collects and writes values from a model (with or without the help of a solver) to file or display (a reporter). The top layer is the application layer (red) which does not provide an API but is a consumer of the OpenSim API to generate applications like the OpenSim GUI or dynamic libraries (plugins) encapsulating model components and/or analyses that are loaded and executed by the GUI at run-time.

    Article Snippet: OpenSim API programmers have full access to the Simbody API as well.

    Techniques: